home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Libris Britannia 4
/
science library(b).zip
/
science library(b)
/
COMMUNIC
/
BULLETIN
/
0801B.ZIP
/
PHNXDOC.2
< prev
next >
Wrap
Text File
|
1987-12-04
|
8KB
|
199 lines
PHOENIX REMOTE COMMUNICATIONS SYSTEM DECEMBER 4, 1987
2.0 PHOENIX HARDWARE REQUIREMENTS
The following are considered the minimum "Baseline" requirements
for running Phoenix:
A. 392K Memory
B. Two Disk Drives
C. Modem
D. Monitor
2.1 MODEMS
Phoenix automatically determines your incoming callers' baud
rates. In order for this to work, your modem must be able to
send NUMERIC result codes, support the Hayes Command Set, and
support DTR (Data Terminal Ready).
The following modems have been tested to work with Phoenix and
are believed to be compatible:
A. Qubie Internal/External (made after August 1985)
B. Rixon PC212A Internal/External
C. US Robotics Courier 2400, MicroLink 2400 & Model 312
D. All Hayes
E. Prometheus
2.2 MODEM SWITCHES
Your modem switches should be set as follows:
1. DTR Normal <under software control-not always on>
2. Display numeric result codes
3. Result codes displayed
4. Modem does not echo commands.
5. Auto answer is on. <optional>
6. Carrier Detect is Normal <not always on>
7. Single phone line.
8. AT Command set is normal. <recognized>
9. Escape Code (+++) will not disconnect.
The above settings are provided for reference only. The numbers
and positions of your modem switches may differ. Be SURE to
consult your modem's manual for the correct settings.
2.3 NUMERIC RESULT CODES
Phoenix determines the baud rate of incoming calls by receiving
the numeric result code from your modem when the modem
establishes carrier detect. Check your (Modem) owner's manual
for these numeric codes. As space permits we will list the
codes for some of the more popular modems below.
PHOENIX REMOTE COMMUNICATIONS SYSTEM DECEMBER 4, 1987
Note that these codes need to be placed in your Phoenix
configuration file created by CONFIG. Phoenix defaults to
the Courier 2400 or Hayes codes listed below:
USR COURIER 2400: ARK 2400 :
300 Baud # 1 300B # 11
1200 Baud # 5 1200B # 5
2400 Baud # 10 2400B # 10
additional for 4800 and 9600 Baud
4800 Baud # 12
9600 Baud # 13
NOTE: Although code for 9600 baud is there and usable, it
has NOT BEEN TESTED AT ALL. If you are adventurous
and use Phoenix at 9600, please let us know of your
findings. We had intended to test this, but could not
get a mfgr to loan us 2 modems within the time frame
for this v1.0 release. We hope to test this and maybe
place 19,200 support in as soon as we can obtain a loan
of 2 modems (USR or FASTCOMM are you listening?).
Therefore, in any baud rate discussions
in this documentation, we will refer to 2400 as a
maximum since that is the fastest rate that Phoenix
has been tested.
NOTE: Some modems require that their "extended" result codes be
initialized before they will display different result codes for
connection between 300, 1200 and 2400 bauds. Some Hayes modems
require an ATX1 sent to the modem. Therefore, if you are using
this type modem, you MUST place the ATX1 command in your
MODMINIT.BBS file! See below.
2.4 MODEM INITIALIZATION
Phoenix automatically sends an "ATZ" and pauses 1.5 seconds
to initialize the modem after each call. Depending on the
modem type, Phoenix will send an "ATA" if needed to answer
the phone line.
This procedure seems to work fine for most modems. However, for
some modems that require an "extended" result mode,
this procedure will not work. For this reason, Phoenix
allows the sysop to send a special initialization string to the
modem INSTEAD of the "ATZ" noted above.
Phoenix will look for a file called "MODMINIT.BBS" in your main
Phoenix directory. If the file is found, Phoenix will read
each line and send that line to the modem until it encounters an
End-of-File. Note that the USR modems usually do not require
a modminit.bbs file unless you wish to turn the speaker off,
or want to keep verbal codes for your terminal program and
have Phoenix switch the modem to numeric.
PHOENIX REMOTE COMMUNICATIONS SYSTEM DECEMBER 4, 1987
A "MODMINIT.BBS" file might look like this:
ATM0 { Turns off the Speaker }
ATH1 { Takes phone off hook during init }
{ NOTE A BLANK LINE CAUSES PHOENIX TO
WAIT 2 SECONDS! }
ATX1 { Turns On Some modems "Extended" result
codes }
ATS0=1 { Answer Modem on first ring }
{ This is needed only if you use carrier detect }
ATV0 { Forces Numeric Result Codes }
ATS7=30 { Set number of seconds the modem will wait
for carrier }
ATH0 { Turns modem speaker back on }
Any legal command YOUR modem will accept will work in the
environment. We can't stress enough that you CONSULT YOUR
MODEM'S OPERATING MANUAL to see what special commands it may
need. Taking the phone OFF HOOK is very important so that
the modem will not answer the phone while digesting its
instructions. If it is allowed to answer the phone, Phoenix
will miss the result code sent and will not respond!
Some modems require extra time to digest certain codes.
In that case, place a blank line after the code to give the
modem 2 seconds. Most use a blank after ATH1, send the rest of
their codes, give a blank line again then ATH0. It is important
to note that you must NOT put a blank line at the end of the
file as Phoenix will wait 2 seconds before getting ready for
a call, and if someone calls during that time, Phoenix will
simply not be able to proceed because the modem will have
sent the code while Phoenix is waiting the 2 seconds.